AP_SCripting: POC using Lua for arming checks #20930
Draft
+190
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amilcarlucas
suggested changes
Jun 8, 2022
timtuxworth
force-pushed
the
arming-check-lua
branch
5 times, most recently
from
aece991
to
7945586
Compare
timtuxworth
force-pushed
the
arming-check-lua
branch
from
7945586
to
e2a132e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a PR for an approach to using lua script to implement arming-checks.
This will allow arming checks to be customizable, and configurable. Checks can be flagged individually as "ERROR" (prevents arming) or WARNING - notifies the grounds station, but arming is allowed.
It will also be possible to easily add or remove checks, for example some partners may want very strict arming checks, some developers may want a more "buyer beware" approach. This accommodates both.